Skip to main content
TrustRadius
Microsoft Intune

Microsoft Intune
Formerly Microsoft Endpoint Manager

Overview

What is Microsoft Intune?

Microsoft Intune (formerly Microsoft Endpoint Manager), combining the capabilities of the former Microsoft System Center Configuration Manager, SCCM or ConfigMgr, is presented as a unified endpoint management option.Microsoft Intune is an endpoint management solution for mobile devices, an MDM solution…

Read more
Recent Reviews

Microsoft Intune Review

9 out of 10
January 17, 2020
Incentivized
We use it for mobile device management, mobile application management, Mac OS management, and Windows 10 management. I have also converted …
Continue reading
Read all reviews

Awards

Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Reviewer Pros & Cons

View all pros & cons
Return to navigation

Pricing

View all pricing

Microsoft 365 Business Basic

$5

On Premise
per user/per month

Microsoft 365 For Individuals

$6.99

On Premise
per month

Microsoft 365 Apps

$8.25

On Premise
per user/per month

Entry-level set up fee?

  • No setup fee

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services
Return to navigation

Product Details

What is Microsoft Intune?

Microsoft Intune (formerly Microsoft Endpoint Manager), combining the capabilities of the former Microsoft System Center Configuration Manager, SCCM or ConfigMgr, is presented as a unified endpoint management option.

Microsoft Intune is an endpoint management solution for mobile devices, an MDM solution that allows the user to securely manage iOS, Android, Windows, and macOS devices with a single endpoint management solution.

The component Endpoint Configuration Manager (the former SCCM) is a system monitoring and management platform that can be deployed as an agent, via the cloud, or on-premises. It can manage systems across OS types (Windows, Mac, Linux), as well as multiple environments, including servers, virtual environments, and mobile devices from a single management console, and supports scaling capabilities, such as future application delivery.

The platform includes a customizable reporting tool to inform future business software decisions. It also enables endpoint protection from malware and vulnerability identification within the monitored systems and infrastructure.

Microsoft Intune Video

Announcing Microsoft Endpoint Manager

Microsoft Intune Integrations

Microsoft Intune Technical Details

Deployment TypesOn-premise
Operating SystemsWindows
Mobile ApplicationNo

Frequently Asked Questions

Reviewers rate Support Rating highest, with a score of 10.

The most common users of Microsoft Intune are from Enterprises (1,001+ employees).
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(312)

Attribute Ratings

Reviews

(1-13 of 13)
Companies can't remove reviews or game the system. Here's why
Sam Othman | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
We are in the process of transitioning from Group Policy over to Microsoft Endpoint Manager. We are using it for controlling our policies and setting up our standard operating environment. as well as application deployment. It allows us to standardize what we are doing and automate IT functions, freeing up valuable resources to be better spent elsewhere.
  • Policy Management
  • Application Deployment
  • Cloud Management
  • Pricing
  • Steep Learning Curve
I would implement Microsoft Endpoint Manager without a doubt in a new startup. Between this and Azure Active Directory, there is limited need for on-prem Group Policy & Active Directory. This would allow full cloud management of the enterprise and less need for on-prem services.

It can be tricky to migrate from on-prem to Microsoft Endpoint Manager within a larger organisation as each individual policy item would need to be implemented one by one and tested thoroughly - but well worth the effort to do this.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
It is being used both across the whole organization and at the department levels. It is centrally managed by the main IT group in the organization, and then individual departments have their own instance of SCCM to be able to use to manage resources/deploy software, etc. It addresses the business problem of having a central Systems Management solution that can pretty much do most everything, including managing all hardware endpoints, managing software, monitoring, asset management, managing antimalware and firewall policies, etc. in an organization.
  • It has nice GUI's built-in for many of the functions throughout the program. This helps to make it easier for the IT Administrator to be able to utilize certain features/functions when using SCCM.
  • It doesn't use a lot of system resources when running, or even if left open on the server. This is good, as it enables those that work with the program to still be productive with being able to run other programs/software on the server.
  • It has really good remote assistance options built-in. This is particularly helpful for the IT Admin being able to assist end-users over a remote session or to remotely connect to computers. This is also a benefit for organizations that don't have a commercial remote assistance product in place.
  • The program itself can be challenging to use, especially if there hasn't been any formal training on the use of the product. Either training/reviewing documentation is recommended prior to using SCCM.
  • At times, it can be difficult to try and find out why a certain machine that's listed in SCCM says that the endpoint has the SCCM client and shows as Active, but in fact, it's not. It's also difficult at times to try and figure out why the client can't be pushed down to the endpoint.
  • Even though the remote assistance features in SCCM are really good, it can be challenging at times when the remote options don't work for a particular endpoint, even though the machine is active, online, etc.
It is well suited in organizations that are looking for an all-in-one Systems Management solution, that is well-known in the industry, and comes from a vendor that is also well-known, and that offers good support for this kind of product. It is less suited for organizations that want to use something right away, without a whole lot of setup/management on the back-end. This also wouldn't be suited for organizations that don't have funding for their IT folks to get formal training in the use of the product or have the time to read through the documentation, etc.
Score 7 out of 10
Vetted Review
Verified User
Incentivized
System Center Configuration Manager was used as a solution for OS deployment, remote troubleshooting, and patch management for Windows PCs in our organization. The plan was to use it to manage close to a thousand PCs in total. As the product required an excessive number of man-hours to implement and support, its use was dropped after a year, and an alternative selected. The main goal was to improve OS deployment and replace WDS.
  • Remote Control works well and does not require a lot of configuration. It must be understood that the Remote Control feature of System Center Configuration Manager is different from RDP, as it does not establish a separate user session and allows a tech to troubleshoot issues in a way visible to a user.
  • It is easy to add client devices for management, and multiple options are available (push, Active Directory, etc.)
  • It's modular and extensible. For example, a third-party company, Parallels, makes a System Center Configuration Manager plugin to manage Macs from the same console.
  • Installation is very laborious and complicated. The number of things to manually configure during the installation is incredible.
  • OS deployment is hard to configure and troubleshoot. The Microsoft article on deploying Windows 10 via System Center Configuration Manager in a test environment takes 44 minutes to read (Microsoft's estimate, not mine -- check here: https://docs.microsoft.com/en-us/windows/deployment/windows-10-poc-sc-config-mgr). If something goes wrong, there are multiple log locations to check on both the server and client, making troubleshooting difficult.
  • The management console looks old, and its performance isn't great. It is often hard to find settings in the console, and it refreshes slowly. The old name for System Center Configuration Manager, SMS, comes to mind often. "Slowly Moving Software."
I know many people have a great experience with System Center Configuration Manager, but it is not suitable for organizations that cannot commit a significant amount of time to configuration and deployment. For example, my organization uses Jamf Pro for Mac management. It took me a couple of days to configure every setting needed for an adequate Mac deployment. System Center Configuration Manager took way longer. Most MSPs in our area do not want to deal with it due to its complexity either. A big organization will find the product more suitable, as configuration tasks are the same whether an organization has 1000 or 10,000 computers, the installation will be more useful with scale. In my case, trying to deploy System Center Configuration Manager as a personal project while doing other tasks was not a success.
Mark Fitzgerald | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Incentivized
We use SCCM for a number of different use cases including imaging, OS and software deployments, inventory and desktop management. Its primary function is to push new software to the fleet. The benefit is being able to time when and what gets deployed and make it done in an automated fashion. We also use it to manage to patch existing software packages (in conjunction with a product called Ninite).
  • You are able to create queries to identify almost any combination of computers needed.
  • Its direct tie to active directory.
  • It fully leverages Windows functionality.
  • Its mac integrations, though improving, are really not much more than inventory.
  • It could benefit from an enterprise remote control solution more similar to Bomgar or LogMeIn.
  • Its web interface for reporting is very dated.
It is an enterprise. You have to have some level of scale to make this product feasible. It isn't just something you throw into the environment to make your life easier. When you are managing thousands of computers, the equation changes and it is incredibly valuable. It is complex and if not done correctly, it potentially can cause a lot of damage, so make sure you fully understand what you are doing before you press the button.
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Currently, we're using Microsoft System Center Configuration Manager to manage all our Windows assets, from PCs to laptops. Considering we use it across all organization, and we have a dozen of remote sites, some of them with distribution points, I can safely say that we solve basically 2 big business problem: We can manage all of those assets from a single pane of glass, delivering software with software-central feature, managing and keeping a eye on the status of those updates and also saving bandwidth at the same time, because we can deploy those software and updates from that distribution point, avoiding to have every single PC/laptop to download from the Internet itself.
  • You can run an inventory of your assets, from PCs to laptops, grouping them by location, type, department, all tight to your own Active Directory. That saves a lot of time when you need to report the status of hardware and software. You can even manage alerts to inform you when some hardware change has happened, which could possibly lead to a robbery.
  • You can centralize software distribution, controlling what kind of software is available for your organization, and here's the most important part: you can give end-users the power to install/remove that software by themselves. That way, you can avoid a ticket to your service desk and potentially save money on those tickets too.
  • Also, due to the distributed architecture of the product, you can deploy a component of the system in each remote site you have. Thanks to that, you can avoid using the bandwidth of the remote site, which usually is already limited, to download software/updates to each PC locally. You just need to download once for the distribution point it will deliver locally. You can also avoid the risk of having your local WAN to be contested by some unexpected outdated PC that was just connected to your network.
  • The licenses can be expensive if you are a small organization. Make sure you have a good deal with your Microsoft partner.
  • Deal with collections can be a little hard sometimes. Collections are the say the product classify or organize the groups. As the concept is a little different from what we're used to, like Active Directory Organizational Units or Security Groups, etc., it's best if you spend some time studying this before you deploy the product in your organization, especially if your organization has severy business or business units and remote sites.
  • You don't have as much product specialists as you have for other Microsoft products like MS Exchange, for example. So, make sure you hire a partner that have the skills needed to help you during the deploy of the product. Indeed, it is a complex product and it demands attention to details to avoid frustration in the future. People tend to save money on the implementation phase and that leads to frustration and, in some cases, projects cancellation due to underestimation of the requirements of the product.
Seems obvious, but if your organization's assets are all based on Microsoft Windows, this is the right product for you. If you have mixed environments, with most of the computers running Linux or Mac, I don't think you'll have the same results. Unfortunately, I can't say much about that, because my experience is only based on a full Windows environment, and honestly, I didn't waste to much time paying attention to other operating systems.
Valery Mezentsau | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User
Incentivized
At my current and previous companies, I have used System Center Configuration Manager as one of the main tools to manage my IT infrastructure. From simple management of active directory users and computers to detailed inventorying of windows equipment (computers and server), software inventorying, software deployments and patch management. Also, it is used as a main endpoint protection solution that includes centrally managed Windows Defender and ATP. We use System Center Configuration Manager as one of the main monitoring tools to get reports of the Windows patching state, device availability and activity, to get information about what PCs users are using at a current time. Using as the only solution to capture and image new and existing workstations and servers. And, also SCCM is the main remote control/assistance tool for our help desk department.
  • We have mostly Windows environments, so SCCM provides us tons of monitoring options for computers and servers.
  • SCCM saves a lot of time and money for our Help Desk team to provide remote assistance to end users.
  • In a Windows 10 environment, SCCM provides pretty decent endpoint protection.
  • Patch management: tons of options of management, deployment, and monitoring.
  • Systems Imaging: deploying images to new PCs or servers, reimaging existed environment.
  • And of course, systems inventorying (hardware and software).
  • Initial configuration is pretty much complex and requires some additional time for preparation and deployment.
  • It would be awesome to have Patch management and endpoint security be moved to separate tabs in the SCCM management console.
  • Imaging functionality is great but over-complicated, and sometimes simple processes take way longer compared to regular WDS services.
  • Better reporting and monitoring services with customized charts.
  • Better integration of SCCM patching services with Windows Updates services on Windows 10. Sometimes it is almost impossible to say if patches were installed on Windows 10 via SCCM deployment until you get that information within SCCM management console.
  • Requires a lot of learning about the product for IT personnel.
This is a great work frame for managing your IT infrastructure. Tons of different options to configure systems, to manage software inventorying and deployments, patch management, systems imaging, etc. It is too hard to find a similar solution with the same number of features and options under the single management console. However, you still need to get third-party products to manage your network and Unix/Linix systems. And, of course, you need to be prepared before starting to use SCCM, it requires a lot of knowledge of the product and predeployment work to be done in advance.
Score 7 out of 10
Vetted Review
Verified User
Incentivized
Our organization is basically using SCCM to deploy some applications remotely, keep a record of each machine we have deployed to users, which is a must have to any organization and also for patching endpoint computers. This last feature would be perfect if it worked consistently, but there are a few complaints.
  • Software deployment - SCCM allow you to silently deploy software to your users without leaving your desk.
  • You can keep track of each machine you deployed.
  • Even though is not perfect, the patching feature is still very helpful.
  • Patching with SCCM is now 100% guaranteed. Sometimes it gets stuck with some patches, other times the patches simply won't show up, but this is just for approximately 10-20% of the devices.
  • For some other features, they could make the path more straight forward, sometimes you need to spend some time in order to find what you want.
  • Sometimes it takes longer for the software you deploy to show up to the user's machine, but that is not an issue, it's kind of 1 in 50 deployments and it just takes a little more time but works.
Well, in my opinion, SCCM is a good tool for any kind of scenario, but if I had to choose I would say it's great mostly for big companies that have hundreds of employees. I wouldn't say SCCM is really needed for small companies with just a few employees where you can do deployments and upgrades manually.
November 30, 2018

SCCM 2012 R2 Review

Score 10 out of 10
Vetted Review
Verified User
Incentivized
Microsoft System Center Configuration Manager is used by our whole IT department. Being part of a company that has multiple locations all across the world, SCCM is a must have tool for managing thousands of computers. SCCM is amazing for imaging, application deployment, and reporting. It allows you to save time and be very efficient.
  • SCCM has a very strong user community.
  • One of SCCM's best feature would be the ability to push software through packages to multiple computers at once.
  • What I like best about this release is the added powershell support.
  • Apart from the steep price, there is absolutely nothing to dislike about this product!
  • Huge learning curve, requires a lot of training.
  • Requires many prerequisites for installing SCCM on a Windows Server.
This software will greatly improve your organization and save you countless hours. If your company is still using Acronis or other small solutions, do them a favor by recommending them SCCM. SCCM is simply the greatest deployment solution on the market. I would highly recommend taking courses to obtain the best performance on the system.
Donald Wildeboer | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User
Incentivized
Our corporation uses System Center Configuration Manager to manage our network of servers. It is being used less and less as we move slowly into the cloud and use the tools that are provided for us there. Our Information Technology department manages the service on behalf of the business lines that need the various servers.
  • We can change the settings on all the different servers using Microsoft Systems Management Server built in tools and interface.
  • The reports that the Microsoft Systems Management Server generates simplifies our process of knowing what computers/servers need to be looked at or upgraded next.
  • Microsoft Systems Management Server ties directly into our Active Directory.
  • Microsoft Systems Management Server is an old tool that we needed to upgrade. We specifically use System Center Configuration Manager that supports Windows 10 and it seems to be keeping up with the times. Sometimes the upgrade was not as easy as we would have liked.
  • The support for other OS's such as Linux and phones is not always the greatest.
System Center Configuration Manager (used to be called Microsoft Systems Management Server) is well suited for a group of servers that are all Microsoft and if you are running a fairly Microsoft Server centric organization. It is good for managing the required changes and configuration of many servers from a central location. It is not always the best at non-Microsoft stuffs.
January 16, 2018

SCCM - Is it worth it?

Score 5 out of 10
Vetted Review
Verified User
Incentivized
SCCM is being used to deploy new workstations, maintain workstation inventory, and apply patches and updates to operating systems and software. Our primary use is new workstation deployment and patching. We also use CM to deploy and manage Microsoft Endpoint Protection on our workstations. This software was purchased to optimize our hire on process.
  • Integration with active directory.
  • Integration with Windows workstations
  • Cumbersome and difficult to configure and manage.
  • Very few ways to manually process tasks; constantly waiting for CM to assess a system and determine if an update is necessary.
  • Requires far too much effort from a technician perspective compared to alternatives. Updating deployment packages, etc.
Large organization where you have enough technicians and can dedicate serious time to managing the system and keeping packages up to date.
January 16, 2018

SCCM 2012 Review

Score 8 out of 10
Vetted Review
Verified User
Incentivized
We use SCCM for image deployment, windows update management, anti virus management with endpoint protection and as a backup remote management tool. Only the IT help desk is using this currently.

We got this in our origination, because Microsoft wanted to assist us in upgrading all of our machines to Windows 10, to move away from Windows 7. We are currently only licensed for workstations and do not actively use it on servers currently, but I believe we will in the future.
  • Anti-virus management. Deploying, managing and removing end point protection is simple. Compared to other products like Symantec, Webroot, Vipre and Trend Micro, threat protection was good and updates were easy. When it was time to remove, it was simple and did not require additional tools to remove the product.
  • Patch management was good. Works well with WSUS and reporting was decent and helped us get caught up on patching that we were lacking.
  • Image management. We have Windows 7 and 10 deployments set up and use SCCM to configure everything for capture and deployment.
  • I would like to see better training and explanation for configuring SCCM to import existing images that have been stood up. While I did manage to get it working, the documentation from Microsoft itself is lacking. I've found that I have to spend a lot of time researching from 3rd parties that have stumbled through it.
  • Remote access to workstations. SCCM remotes in to a machine via the IP and we have found that in an environment where there is wireless and wired and sometimes machines flop back and forth, we cannot always remote in to a machine. If they were able to use the SCCM agent or go by system name, we would be able to remote in to a PC easily and replace the 3rd party tool we have with Dameware.
  • Access restrictions. Doesn't provide an awesome way to lock down what a user can and cannot do within SCCM. We have some level 1 techs that we need to be able to modify a task sequence, but we don't want them to have full admin access.
Really good for internal IT. Would never work for a company that would use it to manage clients. Unless they stood it up per each client and maintained it, this works best for an IT department to manage itself.
November 27, 2017

MIcrosoft SCCM Review

Felix Adusei Tuffour | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Microsoft SCCM is used to manage all workstations either active or inactive found within the company's network domain. It is also used to deploy other resources to these workstations including, windows update, antivirus, and other applications. SCCM is currently being used actively by the IT department and occasionally used by the IT Auditors. The deployment of an antivirus application and other software applications on client machines was a major challenge as this was done on individual client machines which took a long time. With the introduction of Microsoft SCCM, deployment of such activity is done within a shorter period for batches or all machines at once.
  • Deployment of software applications to workstations within the network domain with ease
  • Monitoring of Client machine performance through dashboard activities
  • Ability to customize reports and also an adequate standard report preview
  • Not easily navigable when no proper training has been undergone
Microsoft SCCM is suitable for deploying all corporate software applications to either individual client machines or to a group of client machines.
October 13, 2017

Microsoft SCCM Review

Lawrence S. Patterson | TrustRadius Reviewer
Score 8 out of 10
Vetted Review
Verified User
Incentivized
SCCM is being used to manage users and computers. In coordination with Active Directory, software deployments, updates, device creations and deletions, user account creation, OU management, policy management are some of the activities performed through SCCM. SCCM is being used across the organization for application deployment and reimaging desktops when necessary. Multiple software installations can be performed by creating collections of computers and pushing the installations through the network. Other business problems include inventory of devices and remote connection to resolve troubleshooting matters.
  • Inventory reports can be created for specific O/S, microprocessors or connected monitors can be accomplished for annual computer refreshes.
  • Collections can be created to manage changes to multiple desktops.
  • Policies can be applied to user group for security and other purposes.
  • SCCM doesn't have some of the options that Active Directory provided for managing users or computers. It does have a great deal of flexibility and accessibility.
SCCM is a great tool for managing the application, computer and end-user environment. In coordination with Microsoft Active Directory, LANDESK and SQLServer most tasks are covered and easily accomplished.
Return to navigation